<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
  <meta http-equiv="Content-Type"
 content="text/html; charset=iso-8859-1">
  <meta name="Author" content="makumba-dev">
  <title>Makumba documentation</title>
  <link rel="stylesheet" type="text/css" media="all" href="main.css">
  <script type="text/javascript" src="main.js"></script>
</head>
<body>
<script type="text/javascript">
   makeNavBar("");
</script>
<h1>Makumba documentation</h1>
We try to keep the essential documentation up to date, but some older
parts of the documentation are not reflecting the present situation
entirely.
<h2>User documentation</h2>
<ul>
  <li><a href="makumba-spec.html">Specifications</a>. This covers data
definitions, jsp taglib, etc. The bible. </li>
  <li><a href="api/org/makumba/package-summary.html">Public
API, javadoc</a> </li>
  <li><a href="SQL-drivers.html">Database configuration</a>. How to
configure makumba to talk to your db. </li>
  <li><a href="makumba-example.html">Example</a>. </li>
  <li><a href="faq.html">FAQ</a>. Frequently Asked Questions. </li>
  <li><a href="whitepaper.html">Whitepaper</a>. Explains the original
ideas that sparked the project. </li>
  <li>Advanced: <a
 href="http://cvs.sourceforge.net/viewcvs.py/*checkout*/makumba/makumba/CHANGELOG.txt?rev=HEAD&amp;content-type=text/x-cvsweb-markup">Release
history</a>. The release history is tracked in a raw textfile. </li>
  <li>Advanced: <a
 href="http://bugzilla.makumba.org/query.cgi?product=Makumba">Bugzilla</a>.
For of all bugs and possible enhancements.
    <p></p>
  </li>
  <li><a href="Makumba-reference.pdf">JSP taglib Reference card</a>
(Makumba 0.5.13)</li>
  <li><a href="cleaning-old-applications.html">Cleaning up older
makumba code using new makumba features</a>.</li>
</ul>
<h2><a name="devel">Internal documentation</a></h2>
<p>
These documents are meant to help you understand the internals of
makumba,
e.g. as a starting point for enhancing of bugfixing.
If your only interest is to use Makumba, then you don't need this.
</p>
<ul>
  <li><a href="makumba_design.html">Design issues</a></li>
  <ul>
    <li><a href="issues">prepared workgroup issues</a><br>
    </li>
  </ul>
  <li><a href="makumba_changes_congress_1-2.html">Progress report</a>
between makumba congress 1 and 2<br>
  </li>
  <li><a href="hacking/index.html">Developers introduction to Makumba</a>
  </li>
  <li><a href="hacking/javadoc/index.html">Internal API, javadoc</a> </li>
  <li><a href="http://bugzilla.makumba.org/query.cgi?product=Makumba">Bugzilla</a>.
Tracking bugs, discussing enhancements. </li>
  <li><a
 href="http://cvs.sourceforge.net/viewcvs.py/*checkout*/makumba/makumba/">CVS
repository</a> is holding all sources. </li>
  <li>Out-dated: <a href="makumba.html">Design issues</a>. Reflects
design issues in the early startup. </li>
  <li>Out-dated: <a href="tasks.html">Tasks</a>. From before the use
of Bugzilla. There might be some useful stuff in there. </li>
</ul>
<script type="text/javascript">
   makeFooter("$Id$");
</script>
</body>
</html>
